Skip to content

feat(deploy-component): add install_allow_scripts flag - #636

Merged
kriszyp merged 2 commits into
mainfrom
claude/hopeful-mestorf-92850d
May 20, 2026
Merged

feat(deploy-component): add install_allow_scripts flag#636
kriszyp merged 2 commits into
mainfrom
claude/hopeful-mestorf-92850d

Conversation

@kriszyp

@kriszyp kriszyp commented May 20, 2026

Copy link
Copy Markdown
Member

Summary

  • Adds install_allow_scripts (boolean, optional) to both deploy_component and add_component operations
  • Accepted by both validators in operationsValidation.js
  • For deploy_component: persisted to application config as install.allowInstallScripts (picked up on restart via the existing config-load path in Application.ts:540)
  • For both operations: passed directly to the Application constructor so the immediate install honors it

Purpose

Application.ts already supports install.allowInstallScripts to toggle --ignore-scripts on the underlying npm/yarn/pnpm call, but there was no way to set this flag via the operation API. This wires the missing connection for both operations that perform installs.

Default behaviour unchanged

When omitted, allowInstallScripts is undefined → falsy → --ignore-scripts is used, which was already the default.

Notes

  • add_component does not write to the root config (it clones a template directly), so only the Application constructor is updated there — no config-persistence block.
  • Custom install_command users are unaffected; the flag only controls the default npm/yarn/pnpm invocation path.
  • Cross-model (Gemini) review completed; the add_component gap was flagged by Gemini and addressed in a follow-up commit.

Generated by Claude (agent) — @kris please review

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@claude

claude Bot commented May 20, 2026

Copy link
Copy Markdown
Contributor

Reviewed; no blockers found.

…deploy_component)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@kriszyp
kriszyp marked this pull request as ready for review May 20, 2026 13:00
@kriszyp
kriszyp requested a review from a team as a code owner May 20, 2026 13:00
@kriszyp kriszyp added the patch label May 20, 2026
@github-actions

github-actions Bot commented May 20, 2026

Copy link
Copy Markdown
Contributor

Patch cherry-pick: conflict

Cherry-pick onto v5.0 produced conflicts on commit(s): ebc5cfea776ca2f85661e2dca8f17f57463a491a

The conflict markers are committed on branch cherry-pick/v5.0/pr-636.
A pull request has been opened to land this patch: #637

@kriszyp
kriszyp merged commit 4720676 into main May 20, 2026
40 checks passed
@kriszyp
kriszyp deleted the claude/hopeful-mestorf-92850d branch May 20, 2026 13:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants